Print

This update requires you to make changes to the following files:

• /Web.config
• /App_Config/Include/Sitecore.Analytics.config

The clean config files for Sitecore CMS 6.5.0 and DMS 2.0.1 rev. 121009 can be downloaded using the following links:

• Sitecore CMS 6.5.0 rev. 121009 Web.config file 
• Sitecore DMS 2.0.1 rev. 121009 Analytics.config file 

Changes to the Web.config file

The following changes have been made to the Web.config file of Sitecore CMS 6.5.0 rev. 121009 (Update-6) as compared to the Web.config file of Sitecore CMS 6.5.0 rev. 120706 (Update-5):

1. In the <settings> section, add the following setting:
   
   <!--  ITEM PATHS CACHE SIZE
         Determines the default size of the item paths cache of a database
         Specify the value in bytes or append the value with KB, MB or GB
   -->
   <setting name="Caching.DefaultItemPathsCacheSize" value="10MB"/>
2. For each defined database sections (core, master and web), locate the following section:
   
   <cacheSizes hint="setting">
     <data>20MB</data>
     <items>10MB</items>
     <paths>500KB</paths>
     <standardValues>500KB</standardValues>
   </cacheSizes>
   
   
   In this section, insert an <itempaths> node (default value: 10MB) and repeat for all your Sitecore databases:  
   <cacheSizes hint="setting">
     <data>20MB</data>
     <items>10MB</items>
     <paths>500KB</paths>
     <itempaths>10MB</itempaths>
     <standardValues>500KB</standardValues>
   </cacheSizes>

Changes to the Sitecore.Analytics.config file

The following changes have been made to the Sitecore.Analytics.config file of DMS 2.0.1 rev. 121009 as compared to the Sitecore.Analytics.config file of DMS 2.0.1 rev. 120706.

1. In the <acceptChanges> pipeline, move the DropCancelledPage processor to the very first position in the pipeline. The <acceptChanges> pipeline now looks like this in a default Sitecore installation:
   
   <acceptChanges>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.DropCancelledPage,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.DoNotWrite,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.Robots,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.GeneratingCampaignEvents,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.UpdateAutomationStates,Sitecore.Automation.MarketingAutomation"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.AcceptSharedChanges,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.AcceptChanges.AcceptVisitorChanges,Sitecore.Analytics"/>
   </acceptChanges>
2. In the <pipelines> section, add a new pipeline <excludeRobots>:
   
   <excludeRobots>
     <processor type="Sitecore.Analytics.Pipelines.ExcludeRobots.TryObtainCachedResult,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.ExcludeRobots.CheckUserAgent,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.ExcludeRobots.CheckIpAddress,Sitecore.Analytics"/>
     <processor type="Sitecore.Analytics.Pipelines.ExcludeRobots.AddResultToCache,Sitecore.Analytics"/>
   </excludeRobots>